I think, per the ticket, we could be a little more explicit with our guidance here. It might be helpful to actually list the specific error message a user will get if they omit the database param. That way, a user can search for the specific error message and will find a result that explains the issue and how to resolve the problem.

Can you update this to include the error message, and advise shared-tier users to specify the database param to resolve this error?

Thanks for making this change, @hunter-mongo ! I think we can probably refine the wording further.

First, based on the error message we're documenting, I think the "unless you are on a shared tier" element is not quite accurate. Based on the error message, it seems that even on a shared tier, when you omit the DB param the Source Type still attempts to change to "Deployment." But because shared tier infrastructure does not support deployment changestreams, we reject the change. This may be pedantic, but I would say we could reword this description to something like:

If you omit this parameter, the Source Type changes to "Deployment." However, shared tier infrastructure does not support deployment changestreams. If you omit the database parameter, you receive the deployment changestreams are not supported on shared tier clusters error. Supply the database parameter to resolve this error.

It's more verbose, but I also think it's clearer and more accurate. What do you think?

That is great and I agree that it is clearer!